…rter

Implements the full execution loop in the new session architecture, enabling actual task execution with intelligent caching and formatted output.

Core changes:
- Implement execute_spawn() with fspy tracking for file system access monitoring
- Create PostRunFingerprint for content-based cache invalidation
- Wire up LabeledReporter for formatted execution output with cache status
- Migrate cache to use SpawnFingerprint from vite_task_plan
- Add workspace_path() getter and make session module public

Test infrastructure:
- Add vite-task-smoke e2e test with replace-file-content utility
- Add duration redaction to snapshot tests
- Verify cache hit/miss detection with file modifications

The execution now properly tracks file reads, validates fingerprints, and displays execution progress with cache status indicators.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

Replace ExecuteError enum with event-based error reporting through the Reporter trait. Errors are now emitted as events and stop execution immediately via internal ExecutionAborted error.

Key changes:
- Add Reporter trait with handle_event() and post_execution() methods
- Remove ExecuteError and PathError enums
- Make ExecutionItemDisplay optional in Start event (None for top-level, Some for nested)
- Convert all error returns to error events
- Add internal ExecutionAborted type for error propagation via ? operator
- Update Session::execute to accept Box<dyn Reporter> instead of closure
- Implement Reporter trait for LabeledReporter with error tracking
- Fix top-level leaf execution for built-in commands
- Add cycle dependency error test fixture

All tests pass with updated snapshots.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

Strip .CMD, .BAT, .EXE, .COM extensions from program_name in JSON
snapshots for cross-platform consistency. On Windows, resolved program
paths include these extensions but Unix doesn't use them.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

The program_path field in spawn_command also includes the Windows
executable extension (.CMD) which needs to be stripped for cross-
platform snapshot consistency.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

- Handle both backslash and forward slash variants of paths for
  workspace_root and manifest_dir redaction
- Normalize PATH separator from ; (Windows) to : (Unix) for
  cross-platform consistency

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

cmd.exe doesn't handle quoted arguments with embedded equals signs and
brackets correctly. PowerShell has much better argument parsing that
matches Unix shell behavior.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

cmd.exe needs system environment variables to function correctly.
Instead of clearing all env vars on Windows, only clear them on Unix.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

- Replace platform-specific shell (cmd.exe/sh) with @yarnpkg/shell
  for consistent cross-platform behavior in e2e tests
- Add Node.js experimental warning filtering in redact.rs to handle
  Type Stripping warnings from newer Node.js versions
- Add @yarnpkg/shell 4.1.3 dependency to test_bins
- Use `which` crate to locate shell executable in test_bins

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

When oxlint scans a directory, it uses FindFirstFile/FindNextFile Win32
APIs to enumerate files. Without intercepting these calls, fspy wouldn't
see READ_DIR accesses, causing the cache to miss file additions.

This fix:
- Adds detours for FindFirstFileW and FindFirstFileExW
- Uses GetCurrentDirectoryW for relative patterns like "*"
- Fixes fingerprint.rs to handle paths with trailing backslash

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

NtQueryDirectoryFile is already being intercepted at NT level, which
correctly captures READ_DIR accesses when programs enumerate directories.
The FindFirstFile Win32 API interception was unnecessary as it's just a
wrapper around the NT API.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

On Windows CI, terminal color detection may behave differently, causing
ANSI escape codes to appear in snapshot output even with NO_COLOR=1 set.
Explicitly setting FORCE_COLOR=0 ensures colors are fully disabled.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

The auto-add FORCE_COLOR logic was causing issues on Windows CI where
stdout might be detected as supporting colors even when it's not a TTY.
This caused oxlint to output ANSI color codes in its output.

Changes:
- Add IsTerminal check before auto-adding FORCE_COLOR
- Also check FORCE_COLOR=0 in reporter color detection

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

This reverts commit 2ccb1eb.

…n Windows"

This reverts commit 631f2e0.

… ExitCode>

Use Result type for clearer success/failure semantics:
- Ok(()) for success (exit code 0)
- Err(ExitCode) for failure with specific exit code

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>